Chapter One

Chapter Two

Chapter Three

Chapter Four

Chapter Five

Chapter Six

Chapter Seven

Appendix

Java Computing in the
Enterprise Whitepaper
(Postscript Compressed
141KB)

Java Computing in the
Enterprise Whitepaper
(Acrobat 124KB)

While the industry is just beginning the transition to Java, it is clear that significant functional improvements and economic savings will be realized by adopters. The exact level and nature of these savings will become more apparent over time. It is clear, however, that the savings and functional benefits are significant.

At the same time, the general manager and CIO must run their day-to-day business and solve immediate problems. Summarized below are several recommendations for the general manager and CIO that attempt to balance the management of near-term crises against the requirement for long-term structural change in Java-based information management:

Today:

• Build an enterprise intranet infrastructure using Internet technologies.
• Deploy Java client functionality (webtops) throughout the enterprise, initially through browsers such as Netscape Navigator.
• Move electronic mail to the intranet with access through the webtop. This provides universal access to e-mail from all clients using Internet protocols (IMAP4/SMTP), which work over low or high bandwidth. It also introduces end users to general application access through their webtop (Java-enabled browser or thin client).
• Begin a systematic training program in the MIS department to build Java competence. Many programs are already available from Sun and others.
• Setup organizations whose charter is to build Java applications. A number of commercial integrators can provide help in the transition to Java Computing. Examples include Andersen Consulting, Cambridge Technology Partners, EDS and SunIntegration Services.
• Postpone mass upgrading of client operating systems until an evaluation can be made of superior economics and functionality available through Java. Selective upgrades may be necessary for particular applications or users.
• Track product announcements closely as the numerous Java applications under development make their way to market. Many Java applications are already on the market and by the end of 1996, there should be Java applications available in all major application areas.
• Track industry announcements related to the launch of Java device hardware by many vendors in 1996. Selectively purchase and evaluate Java device hardware in a range of application and user areas.
• Question the acquisition of new fat-client hardware (in all areas except high intensity/high diversity computing) until an evaluation of thin client products is completed.

• Identify dedicated-use applications -- desktops where employees run a small set of custom applications all day long as their job.
• Write or re-write these applications in Java and begin using Java devices in these areas.
• Proposals for system or application changes or upgrades should include the evaluation of the Java option.

• Target early migration of applications to Java in areas where the most immediate benefits appear realizable. Continue thin-client deployment on dedicated-function desktops. Areas of potential immediate return include:
  • Dedicated-function desktops (CMS, reservations, order entry, etc.)
  • Customized decision support applications
  • Customer or supplier communications/transactions
  • Employee communications/transactions

For these last three categories, the ability to access Java applets from any client is a major advantage.

Over next 18 months:

• When a critical mass of Java-based applications has been introduced, begin to replace fat clients with Java devices.